feat(sync): Phase 1 porter workflow + enriched icon/color maps - #67

…ard it (#378)

* chore(sync): derive `icon-map.json` from the shared icon keys, and guard it

Verifies and lands the icon-map content from the closed PR #67, rebuilt rather
than imported.

The map is now **derived**. b24ui and nuxt/ui define the same semantic icon
keys — `src/runtime/dictionary/icons.ts` here, `src/theme/icons.ts` upstream —
so for each of the 37 keys both sides carry, the entry is (upstream's lucide
name -> b24ui's component). Nothing is chosen by eye.

That turned up three wrong values in #67, none of which would have failed an
import because each resolves to a real icon:

- `i-lucide-rotate-cw` where upstream's `reload` is `i-lucide-rotate-ccw`
- `i-lucide-circle-check` for `copyCheck`, whose lucide name is
  `i-lucide-copy-check` (`circle-check` is upstream's `success`, a key we do
  not have)
- `i-lucide-refresh-cw`, which no upstream key uses

and seven derivable pairs it had missed: `drag`, `panelClose`, `panelOpen`,
`star`, `stop`, `copyCheck`, `reload`.

The five entries #67 dropped (`activity`, `arrow-up-to-line`, `house`,
`settings`, `user`) are kept — they match no key on either side, which is
exactly the hardcoded-literal case this table exists for.

#67's five corrections to the committed values are confirmed: `check`,
`chevronDown`, `chevronUp`, `minus` and `x` all pointed at glyphs this library
does not render for those roles.

`test/utils/icon-map.spec.ts` holds the result: every value must resolve in the
installed `@bitrix24/b24icons-vue`, must come from the dictionary (or a
five-entry documented exception list), and must not pick the wrong group for a
name the dictionary already places — 233 icon names exist in more than one
group and 16 of those are in this map, so `solid/RefreshIcon` for
`outline/RefreshIcon` is a live failure mode, not a hypothetical.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JS8ypVfQSFzYVZzkTHhURb

* fix(sync): correct the icon-map's claims, and give its guard teeth

Review follow-up on this branch. Three of the findings were substantive.

**The recorded justification was false.** The changelog said the five corrected
values pointed at "glyphs the library does not render for those roles". It
does render them: `Checkbox.vue` renders `main/CheckIcon` and
`actions/Minus20Icon`, `Badge.vue` renders `actions/Cross20Icon`, `Button.vue`
renders `outline/ChevronDownSIcon`. Roughly half the icon paths under `src/`
are hardcoded in components that never read the dictionary. The corrections
stand — the map must agree with the dictionary — but the reason is restated,
and the underlying inconsistency is now #380.

**The guard did not check the derivation.** Pointing `i-lucide-check` at any
other icon the dictionary genuinely uses passed every assertion. There is now
an explicit `i-lucide-* -> semantic key` table, and each derived row must equal
what that key resolves to; a row disappearing fails too.

**The map was missing the one literal it exists for.** `i-lucide-terminal` is
the only `i-lucide-*` string upstream hardcodes under `src/`, and
`prose/CodeIcon.vue` has answered it all along. The old dictionary-only
allowlist would have rejected it, so the guard's basis widens to any icon used
anywhere in `src/`.

Also: `i-lucide-circle-x` gains a row (our `caution` is commented "this for
error"); the `$schema-note` no longer contradicts itself about `circle-check`;
duplicate JSON keys, which the import silently collapses, are now caught; stray
values report their key; a redundant cast is gone; and both the note and the
changelog now say the guard catches wrong rows, not stale ones.

Not changed: the 37-pair / 43x39 counts. Three reviewers read the installed
`@nuxt/ui@4.8.2` — pulled in transitively by `nuxtseo-layer-devtools`, older
than the sync cursor — and concluded `star` was fabricated. Upstream at
`3dbca02` has it. That trap is now written down.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JS8ypVfQSFzYVZzkTHhURb

---------

Co-authored-by: Shevchik Igor <noreply@anthropic.com>